Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 001 / pibt32e2.arc / README.V32 < prev

Wrap

Text File | 1985-11-30 | 23.2 KB | 623 lines

INTRODUCTION TO PIBTERM v3.2 ============================ The archive files PIBT32E1.ARC, PIBT32E2.ARC, and PIBT32E3.ARC contain a program called PibTerm which provides a terminal emulation and host communications facility. This is version 3.2.5 of Pibterm, released November 30, 1985. This version represents a minor code correction for PibTerm version 3.0, released October 7, 1985. RECENT RELEASE HISTORY ====================== Release 3.0: Released October 7, 1985. Release 3.2: Released November 8, 1985. Release 3.2.1: Fixed bug in CAPTURE script command. Release 3.2.2: Fixed bugs in Ascii upload. Release 3.2.3: Fixed handling of color intensities in ANSI/BBS mode. Release 3.2.4: Fixed handling of redial in script. Release 3.2.5: Added G and L functions in dialing directory. FEATURES OF PIBTERM =================== Features of PibTerm version 3.2 include: 1. Several different terminal emulation methods: -- DEC VT52 -- DEC VT100 (large subset) -- BBS ANSI (ANSI.SYS color graphics and music) -- Dumb glass TTY -- Dumb glass TTY in split-screen mode 2. The ability to act as a host program (mini BBS). 3. Ring buffered, interrupt driven, serial I/O. 4. A number of popular file transfer methods: -- Xmodem Checksum and CRC -- Modem7 batch with either Checksum or Crc -- Ymodem batch or single file -- Telink -- Kermit -- CompuServe "B" Protocol -- Ascii with XON/XOFF -- Autodownload Xmodem for Bob Mahoney's EXEC PC BBS. 5. Telephone dialing directory. 6. Session logging/capture to printer and/or disk. 7. On-screen editing (block mode) for use with mainframes. 8. Menu-driven commands. 9. Macro-key definition, with sufficient capability to provide auto-logon scripts. 10. Escapes to the operating system (and return from DOS) within a PibTerm session. 11. Built-in file and directory manipulation, including directory display, file display, file copying, file erasure. 12. Screen dumps to a file. 13. Customizable modem support. 14. Automatic change of baud rate to the proper one with smart modems like the Hayes 1200 and USR Courier. 15. Built-in phone area code directory. 16. Review buffer for lines scrolled off top of screen. 17. Easy alteration of program parameters to customize to a particular system. 18. Extensive script facility for automating communications chores. Version 3.2 also fixes a number of problems from earlier versions of PibTerm. These archive libraries were created using ARC450.EXE. I assume that if you are reading this file, then you have the proper version of ARC! CONTENTS ======== Archive file PIBT32E1.ARC ------------------------- This archive should contain 2 files, as follows: PIBTERM.COM (Executable files and overlays for PibTerm) PIBTERM.000 Archive file PIBT32E2.ARC ------------------------- This archive should contain 9 files, as follows: PIBTERM.001 PIBTERM.002 PIBTERM.003 (More PibTerm overlays) PIBTERM.004 PIBTERM.005 PIBTERM.006 PIBTERM.007 PIBTERM.008 README.V32 (What you're reading now) Archive file PIBT32E3.ARC ------------------------- This archive should contain 8 files, as follows: PIBTERM.FON (Sample dialing directory) PIBTERM.PRE (Empty dialing prefix file) PIBBW.CNF (Configuration for monochrome monitor) PIBCOLOR.CNF (Configuration for color monitor) VT100.FNC (Key definitions for VT100 keypad keys) CDCNOS.FNC (Key definitions for VT100 under CDC NOS) STRIPHI.TRA (Translate table to strip parity bit) PIBTERM3.DOC (Printable documentation for PibTerm) CHECKING ARCHIVE'S INTEGRITY ============================ After downloading PIBT32E1.ARC, PIBT32E2.ARC, and PIBT32E3.ARC, it's a good idea to verify the integrity of those files using the integrity check feature of ARC450. To perform the check, enter: ARC450 T PIBT32E1.ARC ARC450 T PIBT32E2.ARC ARC450 T PIBT32E3.ARC If the archives pass the integrity check, then you can proceed to extract the files as shown below. If an archive is bad, you can either try downloading it again (although the file may be bad on the BBS you called), or write me for the source + executables disks as described below. DOCUMENTATION ============= Full documentation for PibTerm v3.0 is found in file PIBTERM3.DOC in PIBT32E3.ARC. This documentation also applies to version 3.2. The changes incorporated in version 3.2 are documented in the addendum below. USING PIBTERM ============= To execute PibTerm, extract the files all files from the archive files using the commands: ARC450 E PIBT32E1.ARC *.* ARC450 E PIBT32E2.ARC *.* ARC450 E PIBT32E3.ARC *.* Make sure all the files reside in the same directory. If you have a color monitor and color graphics card, rename the file PIBCOLOR.CNF to PIBTERM.CNF. If you have a monochrome monitor, rename the file PIBBW.CNF to PIBTERM.CNF. Enter PIBTERM in response to the DOS prompt, and away you go! To find out how to execute PibTerm from a different directory, see pages 6 and 7 of the documentation file PIBTERM3.DOC. SOURCE CODE FOR PIBTERM ======================= The source code for Pibterm comprises 35000+ lines of Turbo Pascal. You may be able to find the source archive files PIBT3SP1.ARC through PIBT3SP4.ARC (for version 3.0) on the same BBS from which you obtained this executable version. If not, then you may get the source by sending $12 to: Philip R. Burns Vogelback Computing Center Northwestern University 2129 Sheridan Road Evanston, IL. 60201 The $12 is a media, mailing, and handling cost, not a program charge. You will receive two disks with the complete source of the latest version (currently 3.2) of PibTerm in ARC format, as well as the corresponding executables. RESTRICTIONS ON USE =================== You may also make unlimited copies of the program and distribute these copies as you desire, except that I, Philip R. Burns, reserve the sole right to distribute the program for profit. You may request a duplication charge, not to exceed $10 per copy for the complete executables archive. My original intent was that PibTerm should be used only for academic, educational, and personal hobby use. If you want to use PibTerm in a commercial environment, then you may do so, but I request that you send me a one-time donation of $25 per copy. This donation is ONLY for commercial use; I DO NOT want any money from you for the executable copy unless you are using PibTerm in a commercial environment. Note that this donation is separate from the fee for obtaining the source code noted below. You may use the source code and modify it as you please for NON-COMMERCIAL APPLICATIONS ONLY. You may NOT use the code in developing commercial applications without my permission. I encourage you to extend this program and add interesting new features. I also encourage you to upload these changes to your local BBSs in order to share your work with others. What I do NOT want is for you to rip off this code as if it were yours and sell it for a profit. That's not nice. You should distribute the program without any changes you have made, and then a SEPARATE version with any changes you've made. You should clearly mark the changes in some sort of documentation file, as well as in the source files you change. I also suggest that you add a line to the initial output of PibTerm indicating your name and the date of your modification. THE GD= PARAMETER ================= I left out one important piece of information in the documentation. The configuration parameter GD= specifies the number of hours that local time lags Greenwich mean time. This information is used to adjust the universal time dates received during Ymodem transfers. For example, Chicago generally lags Greenwich mean time by six hours. ADDRESSES FOR ELECTRONIC LETTER BOMBS ===================================== You may leave me messages on the following BBSs: Gene Plantz's BBS (312) 882 4145 Ron Fox's BBS (312) 940 6496 Gene's board is registration only ($15 a year) but well worth it. Ron's board is essentially open, and also worth calling. Thanks, Phil Burns November, 1985 ================================ ADDENDUM FOR PIBTERM VERSION 3.2 ================================ Since the initial release of PibTerm version 3.0, a number of problems have been reported. All of these problems are fixed in release 3.2 which is actually what you will find contained in these archive files. Among the problems fixed are: (1) PibTerm writes directly to screen memory, making it difficult to use under multitasking systems. Solution: Beginning with version 3.2 of PibTerm, you can request that PibTerm NOT write directly to screen memory. Go to the Alt-P menu, request n) miscellaneous, then g) write directly to screen memory, and answer N to the question. PibTerm will then use ordinary BIOS writes. This slows down PibTerm considerably, so use it only when you really have to. The most common reason for not having PibTerm write to the screen is so that PibTerm will execute gracefully under a multitasking executive. I have tried PibTerm under DoubleDos from SoftLogic and it works properly; others have reported some problems with other multitasking programs. Please let me know about these problems so that I can incorporate corrective code in future releases (or you can do it for me!). (2) Script commands are only executed when characters are received from the remote host. Solution: Fixed in version 3.2 -- script commands are checked regardless of whether characters arrive from the remote system or not. (3) The script commands TRANSLATE and KEY don't work. Solution: They work in version 3.2. (4) <TIMEOUT> appears consistently on very fast CPU speed machines, e.g., 8 to 10Mhz AT clones. Solution: Should be fixed in version 3.2; but may still be a problem for some machines. (There is no problem for ordinary PCs and clones.) See also (25) below on RTS/CTS checking. (5) Prefixes for dialing in scripts cause PibTerm to croak; e.g., DIAL "-22" causes PibTerm to die. Solution: Fixed in version 3.2. (6) PibTerm doesn't allow postfix characters in dialing. Solution: Version 3.2 allows you to use the dialing prefix characters as postfix characters. For example, at the dialing prompt, -22+ adds the "-" prefix string to the front of directory entry, and adds the "+" string to the end of the directory entry. (7) Host mode allows null names through. Solution: Null names are not allowed in version 3.2. (8) Host mode messages have the first character truncated. Solution: Fixed in version 3.2. (9) There is no menu entry for the GD= parameter. Solution: There is now -- see Alt-P, n) miscellaneous, f) Greenwich time lag. (10) The foreground color in BBS/ANSI mode always starts out at light grey. Solution: This was intentional, but so many people have complained, that I have changed BBS/ANSI to respond to the same colors as are set up for VT100 mode. (11) Changing communications parameters for Xmodem transfers causes some modems to drop carrier. Solution: In version 3.2, the parameters are only changed when they have to be. Version 3.0 always did the change. (12) The Alt-F directory listing always displays all files in the directory. Solution: In version 3.2 you are prompted for a wildcard for the files to be displayed. (13) Xmodem family file transfers caused machine lockups, especially with the Telink protocol. Solution: This is partly avoided in version 3.2 by not resetting the port when it isn't necessary (i.e., same as fix for #11 above). The rest of the problem concerned a bad use of a pointer variable. Version 3.2 corrects this as well. (14) The file STRIPHI.TRA mentioned in the documentation is missing. Solution: It is now present in PIBT32E2.ARC. (15) Overlay files for PibTerm could be overwritten by a batch mode transfer. Solution: Version 3.2 does not allow the uploading of ANY file whose name begins with the characters 'PIBTERM'. (16) Files create using the C)opy file facility of the Alt-F file manipulation menu were read-only. Solution: Fixed in version 3.2. You can use the public domain program ALTER.COM to change the copy's attributes for those files created using version 3.0. (17) The dialing prefix disappeared during redials. Solution: Fixed in version 3.2. (18) Ascii uploads/downloads ignored ctrl-z end-of-file markers. Solution: This is an option in version 3.2. It is useful for ascii transfers between micros, but probably not useful for most mainframes where the Ctrl-Z is not an end-of-file marker. (19) Ascii transfers don't display the text of lines sent/received. Solution: This is an option in version 3.2. (20) The previous screen contents are lost when executing a jump to DOS using Alt-J. Solution: Version 3.2 restores the previous screen contents after returning from DOS. (21) Redialing for a manually-entered number displays an incorrect name for the system being dialed. Solution: Fixed in version 3.2. (22) The default transfer protocol was always that specified in the PIBTERM.CNF file unless explicitly overriden by the "Alt-P j) file transfer protocol" menu selection. Solution: The default download protocol is changed in version 3.2 each time a new protocol is chosen with either the Alt-R or Alt-S commands. This makes it easier to use the same transfer protocol for a number of transfers in succession without having to explicitly choose a different (non-default) protocol each time. (23) Several people asked for an alternative capture mode in which the observed screen image, after editing backspaces, deletes, tabs, and so on, would be captured rather than the unedited character stream received from the remote system. Solution: To accomodate this, PibTerm v3.2 will ask you if you want an unedited capture (like in v3.0) or an edited capture when you hit alt-O to request a capture. The edited capture saves the edited screen image of each line rather than the unedited character stream from the remote system. In Script mode, the CAPTURE command now has the format: CAPTURE "file name" "capture type" where "file name" is the file to capture to, and "capture type" is either "E" for an edited capture or "U" for an unedited capture. Both the file name and capture type must be enclosed in quotes. IMPORTANT: If you are using a multitasking system, DO NOT REQUEST EDITED CAPTURE unless PibTerm in running in the foreground. Otherwise you may get the screen characters from some other program in the capture file. (24) A new script command KEYDEF provides for defining a function key string without reading in a function key definition file. The syntax of KEYDEF is: KEYDEF keyname "definition" where keyname is the name of the key to be defined (F1-F10,S1-S10,C1-C10,A1-A10) and "definition" is the key definition to be used. (25) RTS/CTS checking caused problems on some machines (i.e., continuous timeouts or lockups). Solution: Version 3.2 allows you to specify if RTS/CTS checking is to be done. (26) The baud-rate adjustment when dialing a system with a modem like the USR Courier sometimes failed and resulted in strange baud rates being set. Solution: Fixed in v3.2 (I hope). (27) Some people complained that the file transfer windows covered information on the underlying screen which they might want to see. Solution: In version 3.2, you can toggle the status display for Xmodem family file transfers on and off by hitting Alt-1. Any error causes the status display to reappear. Also, the display reappears at the end of the transfer. Note that Alt-1 does NOT work for Ascii transfers, and does not yet work for Kermit. Avoid hitting Alt-1 when you have told PibTerm not to write directly to the screen. Updating the entire screen takes enough time that you may introduce timeout errors. Also note that, with a batch transfer, the window for the current file disappears, but the underlying batch file list does NOT disappear. (28) Ascii file transfers sometimes locked up while displaying the "transfer complete" message. Solution: Fixed in version 3.2. (29) IF conditions for local or remote strings sometimes failed to propagate properly in nested structures. Solution: Fixed in version 3.2. (30) There was no way to halt an Ascii upload to host mode from the remote system. Solution: Version 3.2 waits for a Ctrl-Z. (31) The built-in BBS/ANSI driver did not properly display intensified and blinking characters. Solution: Fixed in v3.2.3. (32) The redial command asks for keyboard input in script mode, making it difficult to write scripts for unattended mode operation. Solution: Fixed in version 3.2.4. (33) Version 3.2.5 add two facilities to the dialing directory: (a) G allows direct access to a given page of the dialing directory. For example, entering G3 takes you to the page with entries 31 through 45. (b) L allows you to enter a list of numbers to be dialed in sequence. Up to ten numbers may be so designated. The numbers are dialed in a round-robin sequence until a connection is made or a dialing attempt is terminated by your hitting the ESC key. Prefixes, postfixes, and manual dials may all be requested, in addition to directory entry numbers. My thanks to all those who pointed out these problems and made suggestions for improvements. PibTerm v3.2.5 was released November 30, 1985. SOME COMMON PROBLEMS ==================== Two questions cropped up repeatedly concerning version 3.0: Question: PibTerm won't dial a number; instead it displays a message to the effect that a session is already in progress. How do I get PibTerm to dial??? Answer: Your modem is set so that the carrier detect line is ALWAYS high, indicating an online session, even when NO session is current. You can fix this problem in two ways: (1) Reset your modem so that the carrier detect is NORMAL, i.e., only is high if a session genuinely is in progress. (2) Hit Alt-P for the main configuration menu, hit i) modem setup, then hit n) carrier line high, and answer Y to the question about carrier detect always being high. Question: PibTerm won't talk to my modem -- I keep getting <TIMEOUT> messages. Answer: Your modem or cable doesn't allow for RTS/DSR/CTS line monitoring. Either get a decent modem and cable (!) or go the main PibTerm menu with Alt-P, choose n) miscellaneous, then choose h) and i) and answer N to the questions about Dataset Ready and Clear To Send monitoring. NOTES FOR THE FUTURE ==================== I plan on releasing a version 4.0 of PibTerm sometime around next February. I hope to include SOME of the following features: (1) Modem setups by brand name (i.e., just say "USRCOURIER" and all the modem-related variables are properly initialized). To that end I solicit command lists for whatever modems you are using. (2) A "learning" mode for script files, so that PibTerm can build a script file from an actual session, easing the construction of auto-logon scripts. (3) Emulators for Televideo and Dec VT220 terminals. I'd like to add a graphics terminal as well, but that will be MUCH more difficult. (4) Nested scripts, and a number of extended script facilities, including named variables, CASE statements, more complex expressions for conditional testing, and so on. (5) A few host-mode improvements. (6) File transfer facilities to take advantage of those modems which have built-in error checking like the MultiTech and ARK modems. (7) Kermit improvements, including repeat counts, and whichever of the sliding window or larger packet proposals wins out. (8) Improved VT100 emulation. (9) X.PC protocol. (10) You tell me! Suggestions are always welcome. Code that implements those suggestions is even MORE welcome.